Temporarily use require('node-sass').renderSync to avoid node-sass hang where the same file is imported by multiple other files#109
Conversation
|
All be it a temporary solution, I definitely need this soon. |
|
How and where in webpack should I use renderSync? |
|
If you'd like to try my fork with these fixes, you can do |
|
@hedgepigdaniel tried your solution but it only delays the hanging from 40% to 61% for me, so not a complete fix unfortunately |
|
Mhmmm ... do you know how deasync works? I'm a bit afraid to merge this when deasync is messing with node's event loop. It looks like black magic to me 😀 Can more people try this PR locally? If it fixes the current issues (and deasync is "harmless"), I am willing to merge it. |
|
Issue fixed by #132. But thank you for your effort and your proposal 👍. Although I did not merge it, I do think that these contributions help to improve the code. |
This isn't a good long term solution but it fixes the problem and allows sass files to be compiled properly (if more slowly) by webpack until the bug in node-sass is fixed.